home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
033a
/
useron21.zip
/
USERON.DOC
< prev
next >
Wrap
Text File
|
1991-03-10
|
5KB
|
132 lines
-=( UserOn version 2.0 )=-
What is it:
===========
Useron does almost exacly the same as the useron function of RA 1.0. There's
only one single extra: Whenever a user has the 'external util/door' status
UserOn looks in the RA Directory for a file USERDOES.<NodeNr>. This file
may contain a more accurate description of which door that user entered.
RA only reserves a byte and 6 predefined messages for this purpose, and I
as a doorwrite would like to put the name of the program there.. Alas, this
is not possible with RA, so I wrote this little replacement.
Source code (pascal) for putting, reading and writing such a UserDoes file
is included.
How To:
=======
Simply replace the ShowUsers call with a type 7 call with on the optional
dataline:
<Path>UserOn.exe -T:*T -N:*N [-P:*P] [-SYSOP:ON] [-LINES:<NoLines>]
(The -P is only nessecary when you use a commport different from the one in the
Config.ra, the -N:*N should be there, as this program only makes sence in a
multiline RA setup)
That's all.
Programmers:
============
The USERDOES.<NodeNr> file is a simple textfile with only one line of text,
Maximal 70 characters long. (should be enough..;)
It's expected to be found in the directory where the RA environment variable
is pointing to. Note that the <NodeNr> part has NO leading zeros!
UserDoes.1 is a legal name
UserDoes.001 will never be found.
If you use the DoIt.Pas unit, things are simpler:
Put somewhere in the initialization part of your program the lines:
DoingWhat='Your text which has to appear';
SetDoingInfo(NodeNr);
And at the end of the program a line:
ClearDoingInfo(NodeNr);
CopyWrong: you are encouraged to include this program with your own programs
as long as you include the WHOLE package......
Using this program with existing utils and doors:
=================================================
Well, from a type 7 menuitem with out a batch you're out
of luck until (and IF) the author of the program supports this
way of showing his info.
From a type 15 things are easier, just put a line :
Echo <The text to appear> > c:\RA\userdoes.%1
into the batchfile and things should work! The %1 reflects the nodenr here.
At the end of the batch you can delete the file with a simple
del c:\ra\userdoes.%1
Last words:
===========
Just in case: you're using this program at your own risk! Never will I accept
any responsibility for anything happening due to the behavior of this program!
This program is freeware. Do with it whatever you like. and if you are a
door-programmer yourself, consider supporting the idea.. After all,
when the useron info sais something like:
> User having a good time playing multiline-tradewars
The odds are that other users jump in..;-)
Enjoy!
Gerhard
==============================================================================
Version 2.0
Added the option to send an online message too.. This isn't my way of
providing a real multiline chatter, but it makes things more decent as
the user get's only one UserOn list. Further I provided an editor to
write longer on-line messages.. (up to 20 lines) which can be edited.
As simple line-editor (but it looks great ansi/avatar too...;-)
If you want to give the users the possibility to send online messages
add the parameter -LINES:<NoLines> to the commandline.
If NoLines is 0, NO messages van be send (same as not putting the parameter
on the commandline) if NoLines is greater than 20 the maximal msglength of
20 lines can be used.. Every number in between puts a maximum on the msglength.
If here's already a NODE??.RA found, the text is appended.
==============================================================================
Version 1.2
Found that useron didn't work ok under DV. Found a bug in one of my libraries,
and the problem is solved.
Also added a SysOp override, as I don't want to show up in the 'Users today'
list. (Certainly not while testing..) But have no problems with users seeing
me online.. Just add a -SYSOP:ON to the commandline and you're on the list
whatever the 'ExcludeSysopFromList' field is saying..
==============================================================================
Version 1.1
Removed the LiveSystems commercial on top of the screen and tried to make it
look as much as possible as the RA UsersOn command..
Also fiddled around with the colors a little..